Pull Request for PyVerse 💡

Requesting to submit a pull request to the PyVerse repository.

Issue Title

Title : Interactive Tweet Management System
This pull request aims to add a fully functional interactive tweet management system to the PyVerse repository.

• [ Yes] I have provided the issue title.

Info about the Related Issue

What's the goal of the project?
Describe the aim of the project.

The goal of this project is to provide a user-friendly web application that allows users to manage tweets. The application implements all CRUD (Create, Read, Update, Delete) operations, enabling users to create new tweets, view existing ones, edit them, and delete them as needed. This system leverages the Django framework for the backend, uses HTML and CSS for the frontend, and stores data in a SQLite database.

• [ Yes] I have described the aim of the project.

Name

Please mention your name.

Enter your name here.

Ananya G Shetty

• [Yes ] I have provided my name.

GitHub ID

Please mention your GitHub ID.
Enter your GitHub ID here.
#152715005

• [Yes ] I have provided my GitHub ID.

Email ID

Please mention your email ID for further communication.
Enter your email ID here.
[email protected]

• [ Yes] I have provided my email ID.

Identify Yourself

Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC).
Enter your participant role here.
GSSOC

• [yes ] I have mentioned my participant role.

Closes

Enter the issue number that will be closed through this PR.
Closes: #issue-number
#651

• [ Yes] I have provided the issue number.

Describe the Add-ons or Changes You've Made

Give a clear description of what you have added or modified.
Describe your changes here.
I have implemented a complete Interactive Tweet Management System that enables users to create, view, update, and delete tweets. The project is built using the Django framework, with a responsive user interface designed using HTML and CSS. The backend uses SQLite as the database, ensuring efficient data management. I have also included necessary requirements and setup instructions in the documentation.

• [Yes ] I have described my changes.

Type of Change

Select the type of change:

• Bug fix (non-breaking change which fixes an issue)
• [ Yes] New feature (non-breaking change which adds functionality)
• Code style update (formatting, local variables)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Describe how your changes have been tested.
Describe your testing process here.
I have tested the application locally, ensuring that all CRUD operations work as expected. I also verified the responsiveness of the application across different devices and browsers, confirming that there are no functional issues or errors.

• [Yes ] I have described my testing process.

Checklist

Please confirm the following:

• [ Yes] My code follows the guidelines of this project.
• [ Yes] I have performed a self-review of my own code.
• [Yes ] I have commented my code, particularly wherever it was hard to understand.
• [ Yes] I have made corresponding changes to the documentation.
• [ Yes] My changes generate no new warnings.
• [Yes ] I have added things that prove my fix is effective or that my feature works.
• [ Yes] Any dependent changes have been merged and published in downstream modules.